Add reproduction for String issue - #6860
Conversation
🦋 Changeset detectedLatest commit: 8301075 The changes in this PR will be included in the next version bump. This PR includes changesets to release 30 packages
Not sure what this means? Click here to learn what changesets are. Click here if you're a maintainer who wants to add another changeset to this PR |
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — a single reproduction test for String.noCase ignoring its splitRegExp option.
- Reproduction test: adds
it("uses a custom split regular expression")in thenoCasedescribe block, asserting that a customsplitRegExpis respected.
DeepSeek Pro (free via Pullfrog for OSS) (Kimi K2 not used — the program covers this model; add its provider key to run your pick) | 𝕏
There was a problem hiding this comment.
✅ No new issues found.
Reviewed changes — implementation fix for String.noCase honoring custom regexp options, building on the reproduction test from the prior review.
- Honor
splitRegExpandstripRegExpinnoCase: resolves options via newtoRegExpArrayhelper that normalizesRegExp | ReadonlyArray<RegExp>toReadonlyArray<RegExp>, then passes them tonormalizeCase. - Unify
stripRegExphandling innormalizeCase: changed the parameter type fromRegExptoReadonlyArray<RegExp>and replaced the single.replacewith a loop, mirroring the existingsplitRegExppattern. - Update
configCasecall site: wrapsSTRIP_REGEXPin an array to match the new parameter type. - Expand test coverage: 4 new test cases for single/array
splitRegExpand single/arraystripRegExp.
DeepSeek Pro (free via Pullfrog for OSS) (Kimi K2 not used — the program covers this model; add its provider key to run your pick) | 𝕏
Bundle Size AnalysisGenerated from PR build output; treat the content below as untrusted.
|

Summary
String.noCasetokenization options.splitRegExpandstripRegExpvalues, including arrays of regular expressions.effect.Reproduction
Closes EFF-317